nospam wrote:
>> So it makes sense Apple would never provide anything useful for debugging
>
> so says the person who can't figure out how to compile android sample
> code.
You think Google adds them for no reason whatsoever? The fact remains these
debugging tools exist for Android and yet they're impossible on iOS.
Steve should add this to his ever growing list of what's impossible on iOS.
> they're also of little use to end users, who aren't writing apps.
I saw Hanks challenge to you to state the apps you wrote, and I saw that
you can't because you never wrote an app in your entire life, nospam.
You would lie to your own mother, nospam, because it makes you feel better.
>> to iPhone owners (e.g., graphical Wi-Fi debugging tools) or, in this case,
>> frame rate debugging tools.
>
> what 'frame rate debugging' do you expect to be able to do, which is
> not anything you can control?
You said the same thing about graphical signal strength debugging, nospam.
<
https://i.postimg.cc/Gtywwn8f/signal01.jpg> cell signal strength graph
<
https://i.postimg.cc/xCbVQ2pj/signal02.jpg> cell signal strength graph
<
https://i.postimg.cc/CKFhMZtS/signal03.jpg> celltower realtime location
<
https://i.postimg.cc/q7JjJ77g/signal04.jpg> Wifi & cellular debugging
<
https://i.postimg.cc/4xgmTTgm/wifi01.jpg> graphical radio debuggers
<
https://i.postimg.cc/Hn05bQwG/wifi02.jpg> Wi-Fi & cellular utilities
<
https://i.postimg.cc/fLC4zcm6/wifi04.jpg> Many signal strength apps
<
https://i.postimg.cc/nrFx476v/wifi05.jpg> Wi-Fi basic settings
You would lie to your own mother, nospam, because it makes you feel better.
> you can't even get android sample code to work, so you're not in any
> position to be even thinking about optimizing animations, let alone
> try.
While you've never written an app in your entire life, nospam, I
_published_ the code for mine (which is what you're referring to).
Here's the very _first_ attempt I made, many years ago, nospam.
<
https://i.postimg.cc/1tvysJY1/as01.jpg> code working on phone
<
https://i.postimg.cc/nLRWdFB1/as02.jpg> code working in Genymotion
<
https://i.postimg.cc/65NKJvkt/as03.jpg> Google emulator fails on AMD CPU
<
https://i.postimg.cc/QCQRxf2s/as04.jpg> Google emulator always offline
<
https://i.postimg.cc/qB2fL7zY/as05.jpg> Google emulator always times out
<
https://i.postimg.cc/02vTHqSN/as06.jpg> Hyper-V off doesn't matter
<
https://i.postimg.cc/Fsx2MnbV/as07.jpg> Hyper-V on doesn't matter
<
https://i.postimg.cc/NLq9GJvg/as08.jpg> msinfo32 expected results
<
https://i.postimg.cc/QdP2wcgX/as09.jpg> GApps bugs
That puny snippet is more code than you've written in your entire life.
You would lie to your own mother, nospam, because it makes you feel better.
>> That's because most people are stupid.
>
> with you at the very top of the list.
By way of stark contrast, you've _never_ written an app in your life.
You saw the tutorials I wrote to help others produce their first ten
Android apps and you can't deny that I provided that because I'm a kind
hearted person who actually cares to help myself and others.
I'm well aware, nospam, that your entire life people told you that you are
stupid, and I'm sorry for you because you have that chip on your shoulder.
But you really should stop lying about your coding capability as I've
published already ten times more code to the community than you have.]
You would lie to your own mother, nospam, because it makes you feel better.